feat: artifact support #122

lima-limon-inc · 2025-11-03T20:59:43Z

Closes: #121

This PR adds artifact support, both for executables and libraries. With these changes, midenup should first try to download an artifact if it exists, if it doesn't or the download process fails, then it defaults to install the component from source.

Implementation notes:

The Artifact struct holds a URI which is used to fetch the artifact, either from a URL (prefixed by https://) or from a file (prefixed by file://). Each artifact only holds a specific triplet (for more information, see LLVM's triplet implementation), which is displayed in the URI itself, for example:
- https://github.com/0xMiden/miden-debug/releases/download/v0.4.4/miden-debug-aarch64-apple-darwin: : Holds the miden-debugger's binary for aarch64-apple-darwin
- https://github.com/0xMiden/miden-vm/releases/download/0.0/std.masp: Holds the Package for the std library. (Do note that masp packages are used by the MidenVM and therefore these URIs do not have a platform dependent triplet).
The src/external.rs file holds functions that are imported into the install script by the include_str macro. These were added in a separate file to enhance readability.
As a final note, now if a component fails to get installed, midenup will simply skip said component if it's in release mode. In debug mode, it panics.

lima-limon-inc · 2025-11-06T15:11:19Z

Hi there @bitwalker. Status update: This PR is almost ready for review, I'm doing some final polishing.

Before merging this, I think it would be worthwhile to add an artifact field to at least one component, so that we can check that it works properly. So far, I've been testing this with a simple hello world binary.

Maybe we could try adding the debugger, since that's where the release github action currently resides. Is the next branch ready for merging? Did you have something else in mind?
Do let me know if I can help with anything!

lima-limon-inc · 2025-11-06T15:13:01Z

src/commands/install.rs

+    // bin/ directory which holds binaries.
+    let bin_dir = toolchain_dir.join("bin");
+    if !bin_dir.exists() {
+        std::fs::create_dir_all(&bin_dir).with_context(|| {
+            format!("failed to create toolchain directory: '{}'", bin_dir.display())
+        })?;
+    }
+
+    // lib/ directory which holds MASP libraries.
+    let lib_dir = toolchain_dir.join("lib");
+    if !lib_dir.exists() {
+        std::fs::create_dir_all(&lib_dir).with_context(|| {
+            format!("failed to create toolchain directory: '{}'", lib_dir.display())
+        })?;
+    }
+
+    // opt/ directory which holds symlinks to binaries in bin/.
+    // These are used in order to preserve a "midenup" compatible
+    // interface. This relies on the fact that clap uses argv[0] in order to
+    // display executable names names. These symlinks have the following format:
+    // `miden <component name>`
+    // Then, when `miden` is invoked, it uses these symlinks to execute the
+    // underlying binary.  With this setup, `clap` displays the name as: `miden
+    // <component name>` instead of just `binary_name` when displaying help
+    // messages.


opt/, bin/ and lib/ did not change in this PR. I simply added these lines and comments to elaborate on their functionality.

lima-limon-inc · 2025-11-06T20:49:40Z

src/commands/install.rs

 {%- else if dep.path %}, path = "{{ dep.path }}"
 {%- endif %} }
 {%- endfor %}
+curl = "{{ curl_version }}"


This will use the same version of CURL as the midenup itself. This is obtained in the build.rs file.

lima-limon-inc · 2025-11-07T12:57:56Z

manifest/channel-manifest.json

+          "artifacts": [
+              {
+                  "target": "zkvm-miden-unknown",
+                  "uri": "https://github.com/lima-limon-inc/fabriz.io/releases/download/0.0/std.masp"


These URLS are not intended to be merged and are only here to test this PR. They should be removed before merging.

lima-limon-inc · 2025-11-14T14:50:01Z

Sidenote: I'll give the implementation a rework. I'll replace the triplet to url table with a list of urls instead to simplify things.

bitwalker · 2025-12-31T22:26:17Z

@lima-limon-inc I finally got the the release workflow for miden-debug sorted with artifact (with attestation) support working, with the v0.4.4 release.

v0.4.4 can be used with the v0.19 toolchain, upcoming releases will work with v0.20+. In the meantime, hopefully that provides all that is needed to validate a real component works with this feature.

Signed-off-by: Tomas Fabrizio Orsi <[email protected]>

lima-limon-inc · 2026-01-12T20:57:52Z

@lima-limon-inc I finally got the the release workflow for miden-debug sorted with artifact (with attestation) support working, with the v0.4.4 release.

v0.4.4 can be used with the v0.19 toolchain, upcoming releases will work with v0.20+. In the meantime, hopefully that provides all that is needed to validate a real component works with this feature.

@bitwalker awesome, thanks for the ping!

I have just added the debugger in the 0.19.0 toolchain with its corresponding artifact field in this commit: a85fb79.

It only required doing a small change to the way URI's were parsed, here: 4d295a2. Since the link did not contain the component name (i.e. "debugger"), but rather the repository name (i.e. "miden-debug"). However, this ended up simplifying the implementation all together and actually made the URI's more versatile, since now it can be an arbitrary string as long as the triplet is respected.

I tested on my machine (Apple M3) and the debugger's binary was fetched successfully and I was able to execute it. Here's the output with the corresponding command:

MIDENUP_MANIFEST_URI=file://path/to/local/channel-manifest.json MIDENUP_DEBUG_MODE=true ./midenup install stable

Installing: std.masp
     No artifact found. Proceeding to install from source
     Installed!
Installing: base.masp
     No artifact found. Proceeding to install from source
     Installed!
Installing: vm
     No artifact found. Proceeding to install from source
     Installed!
Installing: client
     No artifact found. Proceeding to install from source
     Installed!
Installing: midenc
     No artifact found. Proceeding to install from source
     Installed!
Installing: cargo-miden
     No artifact found. Proceeding to install from source
     Installed!
Installing: node
     No artifact found. Proceeding to install from source
     Installed!
Installing: debugger
     Fetching artifact
     Installed!

MIDENUP_MANIFEST_URI=file://path/to/local/channel-manifest.json ./miden debugger

WARNING: debugger is installed, but it is not part of the current active toolchain.
error: the following required arguments were not provided:
  <FILE>

(Sidenote: the warning message stems from #123, which got fixed in #124).

bitwalker · 2026-01-13T00:04:39Z

@lima-limon-inc Nice work!

The next release of the compiler will have artifacts as well, just like miden-debug, so that should help with install time considerably.

One thing to note, miden-debug is the name of the executable (corresponding to the convention for commands that are surfaced under the miden CLI, i.e. we'd expect to run the debugger using miden debug). I see that the component name for the debugger you chose was debugger, but I think it might be best for component names to stick close to their executable name, when the component is an executable.

This would mean that we'd end up with the following components currently:

midenc
cargo-miden
miden-vm
miden-debug
miden-client
miden-faucet (or whatever the executable ends up being called)

The non-executable component names are a bit trickier, though I think currently there is only the standard library and protocol library that fall in this bucket. For those, I think we'll want to use the convention of naming the component after the package, e.g. core (std was renamed to core in 0.20) and base (the name of this package will likely change too).

Anyway, wanted to align on that since it came up.

Signed-off-by: Tomas Fabrizio Orsi <[email protected]>

lima-limon-inc · 2026-01-13T14:01:01Z

@bitwalker thanks ^_^.

One thing to note, miden-debug is the name of the executable (corresponding to the convention for commands that are surfaced under the miden CLI, i.e. we'd expect to run the debugger using miden debug). I see that the component name for the debugger you chose was debugger, but I think it might be best for component names to stick close to their executable name, when the component is an executable.

Noted, I've pushed this commit 819ab9f which changes the component's name to debug so that it more closely resembles the underlying binary.

The non-executable component names are a bit trickier, though I think currently there is only the standard library and protocol library that fall in this bucket. For those, I think we'll want to use the convention of naming the component after the package, e.g. core (std was renamed to core in 0.20) and base (the name of this package will likely change too).

Great, thanks for the heads up!

bitwalker · 2026-01-13T19:33:58Z

I'll do one last once-over of this today, and try to get it merged ASAP!

lima-limon-inc self-assigned this Nov 3, 2025

lima-limon-inc added command:midenup An issue or task related to the `midenup` command check:install PRs only: runs workflows that perform additional end-to-end integration testing labels Nov 3, 2025

lima-limon-inc changed the base branch from main to fabrizioorsi/i113-remove-hardcoded-components November 3, 2025 20:59

lima-limon-inc force-pushed the fabrizioorsi/i121-artifact-support branch 4 times, most recently from 77a15c8 to 2fb1bef Compare November 6, 2025 14:47

lima-limon-inc commented Nov 6, 2025

View reviewed changes

lima-limon-inc force-pushed the fabrizioorsi/i121-artifact-support branch 2 times, most recently from f24bcb3 to 0a4ba74 Compare November 6, 2025 17:33

lima-limon-inc marked this pull request as ready for review November 6, 2025 20:47

lima-limon-inc force-pushed the fabrizioorsi/i121-artifact-support branch from d184473 to c82f722 Compare November 6, 2025 20:47

lima-limon-inc commented Nov 6, 2025

View reviewed changes

lima-limon-inc requested a review from bitwalker November 6, 2025 20:53

lima-limon-inc commented Nov 7, 2025

View reviewed changes

Base automatically changed from fabrizioorsi/i113-remove-hardcoded-components to main November 10, 2025 12:46

lima-limon-inc force-pushed the fabrizioorsi/i121-artifact-support branch from 30d37dd to d0d2f32 Compare November 13, 2025 17:52

lima-limon-inc marked this pull request as draft November 14, 2025 14:50

lima-limon-inc marked this pull request as ready for review November 25, 2025 15:52

feat: pass $TARGET triple to crate at compile time

7d0a8df

Signed-off-by: Tomas Fabrizio Orsi <[email protected]>

lima-limon-inc force-pushed the fabrizioorsi/i121-artifact-support branch 2 times, most recently from a747d42 to 68d1af9 Compare January 12, 2026 17:58

lima-limon-inc added 3 commits January 12, 2026 15:27

feat: initial TargetTriple implementation

0eb3380

Signed-off-by: Tomas Fabrizio Orsi <[email protected]>

feat: add Artifacts to Component

52e6b2c

Signed-off-by: Tomas Fabrizio Orsi <[email protected]>

feat: create lib and bin directories before executing the install script

0c974e8

Signed-off-by: Tomas Fabrizio Orsi <[email protected]>

lima-limon-inc force-pushed the fabrizioorsi/i121-artifact-support branch from 68d1af9 to f6eec13 Compare January 12, 2026 19:06

lima-limon-inc force-pushed the fabrizioorsi/i121-artifact-support branch 2 times, most recently from 081b138 to 501a0f9 Compare January 12, 2026 19:39

lima-limon-inc added 17 commits January 12, 2026 16:43

feat: install_artifacts function

db93ae5

Signed-off-by: Tomas Fabrizio Orsi <[email protected]>

feat: add file// support for artifacts

2947434

Signed-off-by: Tomas Fabrizio Orsi <[email protected]>

refactor: move install_artifact to cargo script

0d2e6ce

Signed-off-by: Tomas Fabrizio Orsi <[email protected]>

feat: obtain curl version from Cargo.toml instead of hardcoding it

f7c4a60

Signed-off-by: Tomas Fabrizio Orsi <[email protected]>

refactor: make installation pipeline more linear with booleans

4eab0d8

Signed-off-by: Tomas Fabrizio Orsi <[email protected]>

feat: save downloaded file in .tmp, then rename it when finished

04113b8

Signed-off-by: Tomas Fabrizio Orsi <[email protected]>

feat: fail in debug builds, continue in release mode

af585d5

Signed-off-by: Tomas Fabrizio Orsi <[email protected]>

feat: add artifact support in libraries

a2d94bc

Signed-off-by: Tomas Fabrizio Orsi <[email protected]>

refactor: simplify Triplet struct, use cargo's triplet output as-is

ce8aa71

Signed-off-by: Tomas Fabrizio Orsi <[email protected]>

refactor: replace triplet - Artifact mapping in favor of URI list

851d1bb

Signed-off-by: Tomas Fabrizio Orsi <[email protected]>

refactor: add support for MidenVM artifacts (.masp Libraries)

ecd0363

Signed-off-by: Tomas Fabrizio Orsi <[email protected]>

refactor: remove target from artifact, obtain it from the link itself

0df687b

Signed-off-by: Tomas Fabrizio Orsi <[email protected]>

refactor: remove Artifact::contains, in favor of Artifact::get_uri_for

23fd7e4

Signed-off-by: Tomas Fabrizio Orsi <[email protected]>

nit: remove pub indicator from Artifact

43ef387

Signed-off-by: Tomas Fabrizio Orsi <[email protected]>

docs: expand Artifact documentation

8877199

Signed-off-by: Tomas Fabrizio Orsi <[email protected]>

feat: add debugger with its artifact URI

a85fb79

Signed-off-by: Tomas Fabrizio Orsi <[email protected]>

refactor: don't check if the name matches, only check the triplet

4d295a2

Signed-off-by: Tomas Fabrizio Orsi <[email protected]>

lima-limon-inc force-pushed the fabrizioorsi/i121-artifact-support branch from 501a0f9 to 4d295a2 Compare January 12, 2026 19:46

review: change debugger component name to "debug"

819ab9f

Signed-off-by: Tomas Fabrizio Orsi <[email protected]>

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

feat: artifact support #122

feat: artifact support #122

Uh oh!

lima-limon-inc commented Nov 3, 2025 •

edited

Loading

Uh oh!

lima-limon-inc commented Nov 6, 2025

Uh oh!

lima-limon-inc Nov 6, 2025 •

edited

Loading

Uh oh!

lima-limon-inc Nov 6, 2025 •

edited

Loading

Uh oh!

lima-limon-inc Nov 7, 2025

Uh oh!

lima-limon-inc commented Nov 14, 2025

Uh oh!

bitwalker commented Dec 31, 2025

Uh oh!

lima-limon-inc commented Jan 12, 2026

Uh oh!

bitwalker commented Jan 13, 2026

Uh oh!

lima-limon-inc commented Jan 13, 2026

Uh oh!

bitwalker commented Jan 13, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

feat: artifact support #122

Are you sure you want to change the base?

feat: artifact support #122

Uh oh!

Conversation

lima-limon-inc commented Nov 3, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

lima-limon-inc commented Nov 6, 2025

Uh oh!

lima-limon-inc Nov 6, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

lima-limon-inc Nov 6, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

lima-limon-inc Nov 7, 2025

Choose a reason for hiding this comment

Uh oh!

lima-limon-inc commented Nov 14, 2025

Uh oh!

bitwalker commented Dec 31, 2025

Uh oh!

lima-limon-inc commented Jan 12, 2026

Uh oh!

bitwalker commented Jan 13, 2026

Uh oh!

lima-limon-inc commented Jan 13, 2026

Uh oh!

bitwalker commented Jan 13, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

lima-limon-inc commented Nov 3, 2025 •

edited

Loading

lima-limon-inc Nov 6, 2025 •

edited

Loading

lima-limon-inc Nov 6, 2025 •

edited

Loading